You are here:

Intelligent OTA: Best Practices

Following are suggested practices for moving from the Ayla Developer’s Portal to the Ayla Customer Dashboard.

Test on the Developer Environment - Any new OTA firmware update needs to be tested in the developer environment. This is because the OTA process may not recover from a faulty new image. The process should recover from any errors that occur during the download or from interrupted downloads, but the process does not recover from a faulty OTA.
Be sure to check that you can send an OTA update from the new version as well as to it.
Ramp up on the field environment - Start with 5-10% of field devices with an OTA job, then wait until the job is complete and make sure that all devices that are online have successfully updated to the new firmware version.
Complete deployment in the field environment.
Update all other field devices in blocks of 100-1000 devices.
Make sure that each OTA update is successful for each OTA job.